ci: extend Dependabot coverage to release branches 1.0, 1.1, 1.2 - #297
Open
xyos wants to merge 1 commit into
Open
ci: extend Dependabot coverage to release branches 1.0, 1.1, 1.2#297xyos wants to merge 1 commit into
xyos wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Description of Changes
Adds
.github/dependabot.ymlwithtarget-branchentries so Dependabot version updates cover the active release branches1.0,1.1, and1.2in addition tomain.Dependabot only evaluates the
dependabot.ymlon the repository's default branch, so per-branch coverage must be declared there viatarget-branchentries; a config on the release branches themselves would be ignored. This gap showed up with the recent brace-expansion security fix: Dependabot PR #292 bumpedbuild-tools/oss-attribution/oss-attribution-generator/package.jsononmainonly, and the same vulnerable dependency had to be manually bumped on1.0,1.1, and1.2.The new entries mirror the existing npm update configuration (directory
/build-tools/oss-attribution/oss-attribution-generator, weekly schedule), once per release branch. That directory (withpackage.jsonandpackage-lock.json) was verified to exist and be identical onorigin/1.0,origin/1.1, andorigin/1.2; it is the only npm manifest outsidethird-party-srcon those branches, so no other ecosystems or directories were added.Testing
python3 -c "import yaml; yaml.safe_load(open('.github/dependabot.yml'))".build-tools/oss-attribution/oss-attribution-generator/package.jsonexists onorigin/1.0,origin/1.1, andorigin/1.2viagit ls-tree..github/dependabot.yml(not that it would matter; only the default-branch config is read).Screenshots/Videos
N/A
Additional Notes
Dependabot security updates (as opposed to scheduled version updates) always target only the default branch; the
target-branchentries ensure the release branches at least receive scheduled version-update PRs for this directory.Backporting
Not required. Dependabot reads this configuration from the default branch only, so this change on
mainis sufficient to cover1.0,1.1, and1.2.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.